Qualys VM KnowledgeBase

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index

Attribute	Value
Connector ID	`QualysKB`
Publisher	Qualys
Used in Solutions	Qualys VM Knowledgebase
Collection Method	Azure Function
Connector Definition Files	QualysKB_API_FunctionApp.json
Ingestion API	HTTP Data Collector API — Connector definition requires workspace key (SharedKey pattern)
Custom Log V1 Tables	Yes 🔶 — ingests into tables with type-suffixed columns
Microsoft Learn	View on Learn

The Qualys Vulnerability Management (VM) KnowledgeBase (KB) connector provides the capability to ingest the latest vulnerability data from the Qualys KB into Microsoft Sentinel.

This data can used to correlate and enrich vulnerability detections found by the Qualys Vulnerability Management (VM) data connector.

Tables Ingested

This connector ingests data into the following tables:

Table	Transformations	Ingestion API	Lake-Only
`QualysKB_CL` 🔶	✓	✓	✓
`QualysKnowledgeBase`	✓	✓	✓

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Workspace (Workspace): read and write permissions on the workspace are required.
Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.

Custom Permissions:

Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions.
Qualys API Key: A Qualys VM API username and password is required. See the documentation to learn more about Qualys VM API.

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias QualysVM Knowledgebase and load the function code or click here, on the second line of the query, enter the hostname(s) of your QualysVM Knowledgebase device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.

This data connector depends on a parser based on a Kusto Function to work as expected. Follow the steps to use the Kusto function alias, QualysKB

(Optional Step) Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.

STEP 1 - Configuration steps for the Qualys API

Log into the Qualys Vulnerability Management console with an administrator account, select the Users tab and the Users subtab.
Click on the New drop-down menu and select Users.
Create a username and password for the API account.
In the User Roles tab, ensure the account role is set to Manager and access is allowed to GUI and API
Log out of the administrator account and log into the console with the new API credentials for validation, then log out of the API account.
Log back into the console using an administrator account and modify the API accounts User Roles, removing access to GUI.
Save all changes.

STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

IMPORTANT: Before deploying the Qualys KB connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Qualys API username and password, readily available.

Workspace ID: WorkspaceId

Note: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Primary Key: PrimaryKey

Note: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Qualys KB connector using an ARM Tempate.

Click the Deploy to Azure button below.
Select the preferred Subscription, Resource Group and Location.
Enter the Workspace ID, Workspace Key, API Username, API Password , update the URI, and any additional URI Filter Parameters (This value should include a "&" symbol between each parameter and should not include any spaces)

Enter the URI that corresponds to your region. The complete list of API Server URLs can be found here

Note: If using Azure Key Vault secrets for any of the values above, use the@Microsoft.KeyVault(SecretUri={Security Identifier})schema in place of the string values. Refer to Key Vault references documentation for further details.

Mark the checkbox labeled I agree to the terms and conditions stated above.
Click Purchase to deploy.

Note: If deployment failed due to the storage account name being taken, change the Function Name to a unique value and redeploy.

Option 2 - Manual Deployment of Azure Functions

This method provides the step-by-step instructions to deploy the Qualys KB connector manually with Azure Function. Step 1 - Deploy a Function App

1. Download the [Azure Function App](https://aka.ms/sentinel-qualyskb-functioncode) file. Extract archive to your local development computer.

Follow the function app manual deployment instructions to deploy the Azure Functions app using VSCode.
After successful deployment of the function app, follow next steps for configuring it.

Step 2 - Configure the Function App
1. Go to Azure Portal for the Function App configuration.
In the Function App, select the Function App Name and select Configuration.
In the Application settings tab, select + New application setting.
Add each of the following seven (7) application settings individually, with their respective string values (case-sensitive): apiUsername apiPassword workspaceID workspaceKey uri filterParameters logAnalyticsUri (optional)

Enter the URI that corresponds to your region. The complete list of API Server URLs can be found here. The uri value must follow the following schema: https://<API Server>/api/2.0

Add any additional filter parameters, for the filterParameters variable, that need to be appended to the URI. The filterParameter value should include a "&" symbol between each parameter and should not include any spaces.

Note: If using Azure Key Vault, use the@Microsoft.KeyVault(SecretUri={Security Identifier})schema in place of the string values. Refer to Key Vault references documentation for further details.

Use logAnalyticsUri to override the log analytics API endpoint for delegated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<CustomerId>.ods.opinsights.azure.us.

Once all application settings have been entered, click Save.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index